USB to Coax Bridge

ABSTRACT

A USB-to-coaxial network bridging system and method includes receiving data frames from a USB or FireWire device via a corresponding USB or FireWire communication interface, wherein the received data frames are intended for transmittal to a predetermined remote device on a coaxial network; combining the received data frames into an aggregated frame and addressing the aggregated frame to allow the aggregated frame to be routed to the predetermined remote device on the coaxial network; and sending the aggregated frame to the remote device over the coaxial network.

TECHNICAL FIELD

The disclosed technology relates generally to network communications,and more particularly, some embodiments relate to systems and methodsfor network bridging multiple different networks.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.61/933,700, which was filed on Jan. 30, 2014, and which is herebyincorporated herein by reference in its entirety.

DESCRIPTION OF THE RELATED ART

A local network typically includes several types of devices configuredto share information across the network. For example, one type of localnetwork can be configured to deliver subscriber services throughout ahome, office or other like environment. These subscriber services caninclude delivering multimedia content, such as streaming audio andvideo, to devices located throughout the location. As the number ofavailable subscriber services has increased and they become morepopular, the number of devices being connected in the home network hasalso increased.

The network of FIG. 1 is one example of a multimedia network implementedin a home or office. In this example, a wired communications medium 100is shown. The wired communications medium might be a coaxial cablesystem, a power line system, a fiber optic cable system, an Ethernetcable system, or other similar communications medium. Alternatively, thecommunications medium might be a wireless transmission system. As oneexample of a wired communication medium, with a Multimedia over CoaxAlliance (MoCA®) network, the communications medium 100 is coaxialcabling deployed within a residence 101 or other environment. Thesystems and methods described herein are often discussed in terms ofthis example coaxial network application, however, after reading thisdescription, one of ordinary skill in the art will understand how thesesystems and methods can be implemented in alternative networkapplications as well as in environments other than the home.

The network of FIG. 1 comprises a plurality of network nodes 102, 103,104, 105, 106 in communication according to a communications protocol.For example, the communications protocol might conform to a networkingstandard, such as the well-known MoCA standard. Nodes in such a networkcan be associated with a variety of devices. For example, in a systemdeployed in a residence 101, a node may be a network communicationsmodule associated with one of the computers 109 or 110. Such nodes allowthe computers 109, 110 to communicate on the communications medium 100.Alternatively, a node may be a module associated with a television 111to allow the television to receive and display media streamed from oneor more other network nodes. A node might also be associated with aspeaker or other media playing devices that plays music. A node mightalso be associated with a module configured to interface with aninternet or cable service provider 112, for example to provide Internetaccess, digital video recording capabilities, media streaming functions,or network management services to the residence 101. In addition,televisions 107, set-top boxes 108 and other devices may be configuredto include sufficient functionality integrated therein to communicatedirectly with the network.

With the many continued advancements in communications technology, moreand more devices are being introduced in both the consumer andcommercial sectors with advanced communications capabilities. Many ofthese devices are equipped with communication modules that cancommunicate over the wired network (e.g., over a MoCA Coaxial Network)as well as modules that can communicate over fiber or other networks aswell. Indeed, in many environments, it is becoming more commonplace forthere to be multiple networks, and sometimes multiple differentnetworks, across which a user may wish the network devices tocommunicate. In such circumstances, network bridges can be used to allowdevices to communicate across multiple networks.

Network bridging is a technique for allowing two or more communicationnetworks or network segments to be aggregated. In some cases, theaggregated segments can be combined to form a virtual network. Bridgingtypically relies on a network bridge to connect the multiple networks ornetwork segments. The network bridge can be configured to bridge theprotocols between the two segments or networks, allowing devices on onenetwork to communicate with devices on the other networks, despitedifferences that may exist in specifications of their respective MAC orPHY layers. That is, network bridging can be used to aggregate networksof the same type as well as aggregate disparate networks.

Home media and other devices often include I/O interfaces such as forexample, standardized interfaces like USB, FireWire, and the like. Thesedevices may also include an Ethernet port for Ethernet networkconnectivity. Examples of such devices can include, mobile/smartphones,desktop, laptop and tablet computers, televisions, media players, and soon. USB devices often run applications that, from time to time, requireone USB device to communicate with another USB device via theirrespective USB ports. However, is sometimes desired that one USB deviceconnect with another USB device located in a different room or locationor that is not easily accessible for frequent use. Accordingly, suchdevices need to be relocated so that they can be connected to oneanother via a USB cable between the two.

BRIEF SUMMARY OF EMBODIMENTS

According to various embodiments of the disclosed technology, systemsand methods are provided for bridging a USB-compatible orFireWire-compatible device to a coaxial network. This bridging can beimplemented to open the MoCA connectivity to CE devices, Laptops,tablets, TVs, Computers, home media servers, gaming consoles and otherdevices having standardized interfaces such as USB and FireWire, whichcan use the in home networking, and a reliable connection to Internet,using high speed and high reliability MoCA network. Also, configurationscan be implemented such that for USB and FireWire enabled devices, theusers don't need to externally provide power, or route power to thebridge. For example, the USB interface is able to provide power to thebridge, allowing a plug and play experience and flexible mountingoptions for the bridge. Users can use USB 1, 2, 2.1, 3 and futureversions, or FireWire's past and future versions. Additionally, a bridgecan be split and shared among multiple USB devices using USB hubs orFireWire hubs, and multiple devices can be connected to 1 MoCA tap. Thisbridging can also open the MoCA API such that programmers can developAndroid, Windows, iOS and other applications that run over MoCA homenetwork, and provide connectivity among nodes.

In some embodiments, systems and methods for transferring data from aUSB-compatible device that is not otherwise compatible with a coaxialnetwork, across the coaxial network to a remote device, include: a firstUSB compatible device partitioning data into a plurality of frames, andsending the frames via a USB interface of the first USB compatibledevice to a first USB-to-coaxial network bridge; the firstUSB-to-coaxial network bridge receiving the data frames sent from thefirst USB compatible device via a USB communication interface, whereinthe received data frames are intended for transmittal to a predeterminedremote device on a coaxial network; the first USB-to-coaxial networkbridge combining the received data frames into an aggregated frame andaddressing the aggregated frame to allow the aggregated frame to berouted to the predetermined remote device on the coaxial network; andthe first USB-to-coaxial network bridge sending the aggregated frame tothe remote device over the coaxial network.

In various embodiments, the remote device may be a second USB-compatibledevice that is not otherwise compatible with a coaxial network, or itmay be a coaxially-connected device such as, for example, a televisionset connected through an Ethernet-coaxial bridge or set-top box. Inembodiments in which the remote device is a second USB-compatibledevice, systems and methods can include a second USB-to-coaxial networkbridge receiving the aggregated frame from the first USB-to-coaxialnetwork bridge, and routing individual frames contained in theaggregated frames to the second USB device.

In various further embodiments, routing individual frames contained inthe aggregated frames to the second USB device comprises removing acoaxial network header from the aggregated frame, de-aggregatingindividual frames contained in the aggregated frame, reading addressinformation associated with the de-aggregated individual frames, andtransmitting the de-aggregated individual frames to the second USBdevice based on the address information.

In still further embodiments systems and methods can be implemented inwhich the first USB-to-coaxial network bridge identifies, based onheader information in the received frames, an identification of theremote device and, wherein the addressing comprises, and based on thisidentification, addresses the aggregated frame to the remote deviceusing addressing protocols of the coaxial network. The USB-to-coaxialnetwork bridge can also be implemented such that addressing includesadding a coaxial network frame header to the aggregated frame, thecoaxial network frame header including an IP or MAC address of thepredetermined remote device.

Other features and aspects of the disclosed technology will becomeapparent from the following detailed description, taken in conjunctionwith the accompanying drawings, which illustrate, by way of example, thefeatures in accordance with embodiments of the disclosed technology. Thesummary is not intended to limit the scope of any inventions describedherein, which are defined solely by the claims attached hereto.

BRIEF DESCRIPTION OF THE DRAWINGS

The technology disclosed herein, in accordance with one or more variousembodiments, is described in detail with reference to the followingfigures. The drawings are provided for purposes of illustration only andmerely depict typical or example embodiments of the disclosedtechnology. These drawings are provided to facilitate the reader'sunderstanding of the disclosed technology and shall not be consideredlimiting of the breadth, scope, or applicability thereof. It should benoted that for clarity and ease of illustration these drawings are notnecessarily made to scale.

FIG. 1 is a diagram illustrating one example of a home networkenvironment with which the systems and methods described herein can beimplemented.

FIG. 2 is a diagram illustrating an example implementation of a bridgingdevice in accordance with one embodiment of the systems and methodsdescribed herein.

FIG. 3 is a diagram illustrating one example of a USB device (e.g., aUSB device 161 or 162) that can be connected to a coaxial network usinga USB-coaxial bridge in accordance with embodiments of the technologydisclosed herein.

FIG. 4A is a diagram illustrating an example Coaxial bridge 132 inaccordance with one embodiment of the systems and methods describedherein.

FIG. 4B is a diagram illustrating another example Coaxial bridge 132 inaccordance with one embodiment of the systems and methods describedherein.

FIGS. 5 and 6 are operational flow diagrams illustrating an exampleprocess for bridging USB devices with a coaxial network in accordancewith one embodiment of the systems and methods disclosed herein.

FIG. 7 is a diagram illustrating an example process for networkexploration via a USB-to-coax bridge.

FIG. 8 is a diagram illustrating an example implementation of aUSB-to-coax bridge in accordance with one embodiment of the systems andmethods described herein.

FIG. 9 is a diagram illustrating an example network in accordance withone embodiment of the technology described herein.

FIG. 10 illustrates an example computing module that may be used inimplementing various features of embodiments of the disclosedtechnology.

The figures are not intended to be exhaustive or to limit the inventionto the precise form disclosed. It should be understood that theinvention can be practiced with modification and alteration, and thatthe disclosed technology be limited only by the claims and theequivalents thereof.

DETAILED DESCRIPTION OF THE EMBODIMENTS

The technology disclosed herein is directed toward systems and methodsfor bridging USB-capable devices with a communications network such thatUSB devices can communicate with one another across a non-USBcommunication network, or with other non-USB devices on the non-USBcommunication network.

From time to time, the disclosure provided herein is described in termsof bridging USB devices with a MoCA network. After reading thisdescription, one of ordinary skill in the art will understand how thetechnology disclosed herein can be applied to bridging USB devices toother networks or network types, or to bridging other non-networkinterface devices such as, for example, FireWire devices, to acommunication network.

FIG. 2 is a diagram illustrating an example implementation of a bridgingdevice in accordance with one embodiment of the systems and methodsdescribed herein. Particularly, the example illustrated in FIG. 2depicts the implementation of a USB-to-coaxial bridge they can beimplemented to allow interoperability between USB devices and a coaxialnetworks such as, for example, the MoCA network. Referring now to FIG.2, this example illustrates 2 USB devices 162, 163 configured tocommunicate with one another over a coaxial network 144 via theircorresponding USB-to-coaxial bridges 132, 133.

To illustrate the operation of the technology disclosed herein at a highlevel consider a first example in which USB device 162 is intending totransmit data to USB device 163. Further assume that USB devices 162 and163 are located in different rooms or in locations otherwise making itinconvenient or impossible to connect them using standardized USBcabling. However, you must be devices 162 163 may each be located withina convenient distance of an access point to coaxial network 144.Accordingly, in this scenario, a USB device 162 can be configured tocommunicate the data to be transmitted to USB-to-coaxial bridge 132 fortransmission to USB device 163 across coaxial network 144.USB-to-coaxial bridge 132 can be configured to translate the datapackets received from USB device 162 into data packets compatible withcoaxial network 144. USB-to-Coax bridge 132 negotiates forcommunications bandwidth with the coaxial network controller, and at theallocated time, sends the data packets across coaxial network 144 to theintended device. In some instances, the intended device may be a MoCAdevice or other device compatible with coaxial network 144, while inother embodiments the intended device may be USB device 163. In thelatter case, the data packets are sent across coaxial network 144 toUSB-to-Coax bridge 133, which receives the packets, reformats them intoa packet type expected by USB device 133 and sends the reformattedpackets to USB device 133. Accordingly, as this example serves toillustrate, USB-to-Coax bridge 132, 133 can be used to bridge USBdevices with a coaxial network such as, for example, a MoCA network.

Before describing the technology in further detail, it is useful todescribe an example article of equipment with which the technology canbe implemented. One such example is that of a USB device (e.g., a USBdevice 161 or 162) with communication interfaces interfaces such as thatshown in FIG. 3. After reading this description, one of ordinary skillin the art will appreciate that the technology disclosed herein can beused with any of a number of different devices or equipment havingvarious communication capabilities, including a FireWire interface inaddition to or in place of the USB interface.

With reference now to FIG. 3, in this example application, the exampleUSB device 162 includes a communication module 201, a processor 206(which can include multiple processors or processing units), and memory210 (which can include memory units or modules of different types).These components are communicatively coupled via a bus 212 over whichthese modules may exchange and share information and other data.Communication module 201 includes wireless transceiver module 202, a USBcommunications interface module 204, and an I/O interface module 208.

An antenna 214 is coupled to wireless transceiver module 202 and is usedby wireless transceiver module 202 to transmit radio signals wirelesslyto wireless equipment with which it is connected. These RF signals caninclude information of almost any sort that is sent or received by USBdevice 162 to/from other entities. For example, in the case of a laptopthis can include files such as downloaded music, movies or other audioand video content.

The wireless communications implemented using communication module 201can be implemented according to a number of different wirelessprotocols, including standardized protocols. Examples of suchstandardized protocols include Bluetooth®, HiperLan, and various IEEE802.11 communications standards, although other communication interfaces(whether or not standardized) can be implemented.

A USB interface module 204 is also provided to allow the device tocommunicate with other USB-capable devices via the standardized USBinterface. The USB interface transfers signal and power over a four-wirecable with endpoint connections defined by the USB standard (e.g., theUSB 3.1 standard). Although not illustrated in FIG. 3, the USB device162 would typically also include a standardized USB connector that canbe used to connect the USB device 162 to other USB devices usingstandardized USB cabling.

An I/O interface module 208 is provided in the illustrated example, andcan be configured to couple USB device 162 to other network nodes. Thesecan include nodes or equipment. In this example architecture, the I/Ointerface module 208 includes a receiver module 218 and a transmittermodule 220. Communications via the I/O interface module can be wired orwireless communications, and the transmitter and receiver containedtherein can include line drivers and receivers, radios, antennas orother items, as may be appropriate for the given communicationinterfaces. Transmitter module 220 may be configured to transmit signalsthat can include voice, data and other communications. These may be sentin a standard network protocol if desired. Receiver module 218 isconfigured to receive signals from other equipment. These signals caninclude voice, data and other communications from the the otherequipment, and can also be received in a standard network protocol ifdesired. In terms of the above examples of an MFP or digital camera, I/Ointerface 208 can provide a hardwired complementary interface to thewireless interface described above. This may be, for example, anEthernet interface, a FireWire interface, but as anor other hardwiredinterface.

Memory 210, can be made up of one or more modules of one or moredifferent types of memory, and in the illustrated example is configuredto store data and other information 224 as well as operationalinstructions that may be used by the processor to operate USB device162. The processor 206, which can be implemented as one or more cores,CPUs, DSPs, or other processor units, for example, is configured toexecute instructions or routines and to use the data and information inmemory 210 in conjunction with the instructions to control the operationof the USB device 162. For example, image-processing routines, such ascompression routines, can be stored in memory 210 and used by processor206 to compress image files from raw files into JPEG files.

Other modules can also be provided with the USB device 162 depending onthe equipment's intended function or purpose. A complete list of variousadditional components and modules would be too lengthy to include,however a few examples are illustrative. For example, a separatecommunication module 224 can also be provided for the equipment tomanage and control communications received from other entities, and todirect received communications as appropriate. Communication module 224can be configured to manage communication of various information sent toand received from other entities. Communication module 224 can beconfigured to manage both wired and wireless communications.

A separate control module 226 can be included to control the operationof USB device 162. For example, control module 226 can be configured toimplement the features and functionality of USB device 162. Functionalmodules 228 can also be included to provide equipment functionality. Forexample, in the case of an MFP, various modules (which may includevarious forms of hardware and software) can be provided to performprinting, scanning, faxing, and copying operations of the device. In thecase of a laptop computer, functional modules 228 can include modulessuch as, for example, disk drive modules, solid-state drives, softwareapplications, and so on, and so on. Again, as these examples illustrate,one of ordinary skill in the art will appreciate how other modules andcomponents can be included with USB device 162 depending on the purposeor objectives of the equipment.

Having thus described an example device with which the technology may beimplemented, the technology disclosed herein may from time-to-timedescribed herein in terms of this example application. Description interms of this environment is provided to allow the various features andembodiments of the invention to be portrayed in the context of anexemplary application. After reading this description, it will becomeapparent to one of ordinary skill in the art how the invention can beimplemented in different and alternative environments and applications.

FIG. 4A is a diagram illustrating an example USB-to-Coax bridge 132 inaccordance with one embodiment of the systems and methods describedherein. As illustrated in FIG. 4A, USB-to-coax bridge 132 includes a USBinterface 134 in a coaxial interface 136. As described in more detailbelow, USB-to-coax bridge 132 can be configured to provide a bridgebetween USB devices and the coaxial network such as, for example, a MoCAnetwork. A more detailed description of an example implementation of aUSB-to-coax bridge 132 is provided below with reference to FIGS. 4B and7.

FIG. 4B is a diagram illustrating another example Coax bridge 132 inaccordance with one embodiment of the systems and methods describedherein. In the example illustrated in FIG. 4B, the coaxial bridge 132includes the capability to bridge either or both a USB device and aFireWire device to a coaxial network. This is similar to the deviceillustrated in FIG. 4A, but with the added capability of bridging notonly a USB device to the network but also a FireWire device. Referringnow to FIG. 4B, this example also includes a coaxial network interface136 and a USB interface 134. In addition, this example includes aFireWire interface 152 to allow USB-to-coaxial network bridge 132 2bridge to FireWire-capable devices. To accommodate this, a USB toEthernet module 152 can be included to provide the interface andprotocol conversions to allow the bridge to interface to USB devices.Likewise, a FireWire to Ethernet module 154 can be included to providethe interface and protocol conversions to allow the bridge to interfacewith FireWire devices. Similarly, a mocha/Ethernet PHY bridge 150 can beprovided to bridge the physical layers between the coaxial network andthe USB and FireWire networks.

For ease of discussion, this document is generally drafted to refer to aUSB-to-coaxial network bridge as an example implementation. As willbecome apparent to one of ordinary skill in the art after reading thisdescription, a USB-to-coaxial network bridge (e.g., USB-to-coaxialnetwork bridge 132) can be implemented as a FireWire-to-coaxial networkasked bridge, a USB-to-coaxial network bridge, or a combinedFireWire/USB-to-coaxial network bridge. As will also become apparent toone of ordinary skill in the art after reading this description, such abridge can be implemented to provide bridging between a coaxial networkand virtually any standardized communication interface such as, forexample, USB, FireWire, and so on.

In various embodiments, the bridge can be implemented as an extra donglethat can be connected to an existing coaxial wall plate or other coaxialnetwork interface. In alternative embodiments, the bridge can beimplemented as an in-wall plate that can provide one or more connectionsfor a standardized interface such as USB or FireWire. This can allowplug-and-play connectivity such that the user can simply connect his orher USB or FireWire device directly to the wall plate using astandardized USB or FireWire interface cable (or other standardizedinterface). The bridge can be implemented to connect with any of anumber of coaxial network types including, mocha, for example. This canbe used to leverage the existing coaxial cable network in the home,office, or other environment. Accordingly, the otherwise relativelyshort range or limited connectivity of standardized interfaces such asUSB and FireWire can be extended to span a bridge coaxial network,allowing connectivity of USB and FireWire devices from room to room,floor to floor, and so on.

FIGS. 5 and 6 are operational flow diagrams illustrating an exampleprocess for bridging USB devices with a coaxial network in accordancewith one embodiment of the systems and methods disclosed herein.Particularly, FIGS. 5 and 6 are operational flow diagrams illustratingan example in which a USB-to-coax bridge such as, for example,USB-to-coax bridge 132, receives data from a USB device can communicatetheir data over a coaxial network to a remote node on the coaxialnetwork. At operation 502 a host application on the sending USB devicedetermines that it has data to send to a remote node. The data can be,for example, any of a number of different types of data or content. Forexample, the sending USB device may be a computer that receives videocontent via the Internet and the application has been instructed to sendvideo content to a nether device across the coaxial network.

In this example, the host application sends the data to be transmittedto a network stack. The network stack partitions the data into packetsor frames suitable for transmission via the device's USB port and sendsthose frames to the host USB driver. This is illustrated at operations504 and 506. At operation 508, the host USB driver since the frames tothe USB-to-coax bridge via the USB interface.

At operation 510, the USB-to-coax bridge receives the frames from theUSB device over the USB interface. For example, the USB-to-coax bridgemay receive the frames via USB port 134 (FIG. 4). At operation 512, theUSB-to-coax bridge aggregates the received frames into one or morecoaxial network frames and adds a coaxial network header to each coaxialnetwork frame. For example, in the case of a MoCA network, theUSB-to-coax bridge aggregates received USB packets (e.g., Ethernetpackets) into one or more MoCA packets and adds a MoCA header forrouting across the MoCA network. For example, in some embodiments, thebridge can be configured to identify, based on header information in thereceived frames, an identification of the predetermined remote deviceand to use this identification to address the aggregated frame to thepredetermined remote device using addressing protocols of the coaxialnetwork.

At operation 514, the USB-to-coax bridge makes a reservation request tosend the aggregated packet or packets across the coaxial network. Forexample, the USB-to-coax bridge requests transmission slots from thenetwork controller according to the network's standard MAC protocol.

Once the USB-to-coax bridge receives the bandwidth allocation from thenetwork controller, it sends the arrogated frames across the coaxialnetwork to the remote node. This is illustrated at operations 516 and602. The remote node receives the network packet, removes the coaxialnetwork header, and deaggregates the received frames to recover theoriginal USB-compatible frames sent by the sending USB device. This isillustrated at operations 604, 606 and 608. At operation 610, the remotenode sends the deaggregated frames to the network device via its USBinterface (e.g. USB interface 134). In various embodiments, this routingcan include removing a coaxial network header from the aggregated frame,de-aggregating individual frames contained in the aggregated frame,reading address information associated with the de-aggregated individualframes, and transmitting the de-aggregated individual frames to a USBdevice associated with the address information.

In various embodiments, the USB-to-coax bridge can be configured to workin conjunction with USB device to explore the network. FIG. 7 is adiagram illustrating an example process for network exploration via aUSB-to-coax bridge. In this example, at operation 702, when a USB deviceconnects to the USB-to-coax bridge the first time, it sends an initialping with and exploratory packet. This can, for example, comprise anaddress resolution protocol (ARP) probe packet that can be used to probethe network devices.

At operation 704, the USB-to-coax bridge receives the packet,reformatted for the coaxial network, and broadcasts the packet acrossthe coaxial network. For example, in one embodiment, the USB-to-coaxbridge broadcasts the packet to every node on the coaxial network andwaits for a reply. At operation 706, the receiving nodes examined thepacket to determine whether they meet the criteria set forth in thepacket. At operation 708, nodes that meet the criteria reply to theUSB-to-coax bridge, and the USB-to-coax bridge learns (and stores) whichnode is the appropriate node for a given transmission. If multipleremote nodes reply, the system can be configured to allow a negotiationbetween the replying remote nodes so that one can be elected for thesecommunications.

As the above example serves to illustrate, in various embodiments, theARP packet includes sufficient information to enable receiving devicesto determine whether they meet the criteria sought by the exploringdevice. For example, a new computer being added to the coaxial networkvia the USB-to-coax bridge interface may desire to access the Internetor locate a particular URL. The USB-to-Coax bridge connected to theexploring USB device broadcasts the packet to the member nodes on thecoaxial network. If a network node (e.g., a gateway) receives thepacket, and knows that the URL requested is an Internet URL, and knowsthat it can access the Internet, that network node sends a response backto the USB-to-coax bridge. The USB-to-coax bridge now knows that it isconnected to a computer on the USB-to-coax bridge side and that there isa gateway on the other side. Accordingly, the USB-to-coax bridge can beused to explore the topology of the network.

As another example, consider a high definition television connected to aMoCA network. Television has an IP address on the network. A computerconnected to the USB port of a USB-to-coax bridge also has an IPaddress. Where the computer is looking to stream video it can connect,explore the network, and learn which devices on the network can streamvideo (or learn other capabilities of devices on the network).Accordingly, when an application on the computer selects a television towhich to stream video, the application knows the IP and MAC addressesfor that television. In this example, the computer can be configured tostream the video in Ethernet frames with the appropriate MAC and IPaddresses for the television. When these packets reach the USB-to-coaxbridge, the UCP reads the Mac address and adds the appropriate MoCAheader. The USB-to-coax bridge then forwards the original payload with aMoCA header across the MoCA network. The MoCA header is used to routethe packet to the appropriate node (e.g., the designated TV or itsassociated set-top box), and that node unpacks the Internet content fromthe MoCA packet.

Although the above processes of FIGS. 5, 6 and 7 are described in termsof USB frames, one of ordinary skill in the art will understand afterreading this description how a coaxial bridge can be implemented tobridge a FireWire or other like standard interface to the coaxialnetwork. For example, a FireWire bridge can be implemented to aggregateFireWire frames into a mocha packet for communication across a mochanetwork and the aggregate the frames at the receiving end.

FIG. 8 is a diagram illustrating an example implementation of aUSB-to-coax bridge in accordance with one embodiment of the systems andmethods described herein. Referring now to FIG. 8, this exampleUSB-to-coax bridge 132 includes a memory 810, a processor 806, a bridgemodule 824, a USB interface module 804, a coaxial network interfacemodule 806, a USB connector 827, and a coaxial connector 829. Thesecomponents in this example are communicatively coupled via a bus 813over which these modules may exchange and share information and otherdata.

Memory 810, can be made up of one or more modules of one or moredifferent types of memory, and in the illustrated example is configuredto store data and other information as well as operational instructionsthat may be used by the processor to operate USB-to-coax bridge 132. Theprocessor 806, which can be implemented as one or more cores, CPUs,DSPs, or other processor units, for example, is configured to executeinstructions or routines and to use the data and information in memory810 in conjunction with the instructions to control the operation of theUSB-to-coax bridge 132. For example, bridge communications routines,such as packet aggregation and de-aggregation routines, can be stored inmemory 810 and used by processor 806 to convert packets from USB to MoCAand vice versa.

A separate bridge module 824 can be included to control the operation ofUSB-to-coax bridge 132. For example, bridge module 824 can be configuredto implement the features and functionality of USB-to-coax bridge 132.

A USB interface module 804 is also provided to allow the USB-to-coaxbridge to communicate with USB-capable devices via the standardized USBinterface using a standardized USB connector 827. Likewise, the coaxialnetwork interface module 808 is provided to allow the USB-to-coax bridgeto communicate with the coaxial network. Inappropriate coaxial cableconnector 829 is also shown to provide the physical interface to thecoaxial network.

FIG. 9 is a diagram illustrating an example network in accordance withone embodiment of the technology described herein. The exampleillustrated in FIG. 9 depicts an example scenario of usingUSB-to-coaxial network bridges to enable USB devices (e.g., devices thatcannot otherwise connect to the coaxial network) to connect to andtransfer data across the coaxial network. The example in FIG. 9 shows anexisting MoCA network 815 with a plurality of conventional MoCA nodes.Particularly, high definition televisions 841 are connected to the MoCAnetwork utilizing Ethernet coaxial bridges 834 and a multiroom DVR 842.Available unused ports 843 are also illustrated in as are a connectionfor the Internet, television, or other services 844 that can be madeavailable to the nodes over the mocha network.

This example also shows the extended mocha network 817 extended by theuse of bridges. In this example, USB-coaxial bridges 832 are used,however, in other embodiments FireWire or other bridges can also beused. Here, a desktop computer 851 and a high definition television 852are connected to the network via their respective USB-coaxial bridges832. Also, a plurality of devices (in this instance computers) 846 areconnected to the network via a single USB-coaxial bridge 832 using a USBhub. Accordingly, as this example illustrates, multiple USB devices(e.g. 851, 852, 846) can communicate across the mocha network to othernodes using the bridges.

As used herein, the term module might describe a given unit offunctionality that can be performed in accordance with one or moreembodiments of the technology disclosed herein. As used herein, a modulemight be implemented utilizing any form of hardware, software, or acombination thereof. For example, one or more processors, controllers,ASICs, PLAs, PALs, CPLDs, FPGAs, logical components, software routinesor other mechanisms might be implemented to make up a module. Inimplementation, the various modules described herein might beimplemented as discrete modules or the functions and features describedcan be shared in part or in total among one or more modules. In otherwords, as would be apparent to one of ordinary skill in the art afterreading this description, the various features and functionalitydescribed herein may be implemented in any given application and can beimplemented in one or more separate or shared modules in variouscombinations and permutations. Even though various features or elementsof functionality may be individually described or claimed as separatemodules, one of ordinary skill in the art will understand that thesefeatures and functionality can be shared among one or more commonsoftware and hardware elements, and such description shall not requireor imply that separate hardware or software components are used toimplement such features or functionality.

Where components or modules of the technology are implemented in wholeor in part using software, in one embodiment, these software elementscan be implemented to operate with a computing or processing modulecapable of carrying out the functionality described with respectthereto. One such example computing module is shown in FIG. 10. Variousembodiments are described in terms of this example-computing module 900.After reading this description, it will become apparent to a personskilled in the relevant art how to implement the technology using othercomputing modules or architectures.

Referring now to FIG. 10, computing module 900 may represent, forexample, computing or processing capabilities found within desktop,laptop and notebook computers; hand-held computing devices (PDA's, smartphones, cell phones, palmtops, etc.); mainframes, supercomputers,workstations or servers; or any other type of special-purpose orgeneral-purpose computing devices as may be desirable or appropriate fora given application or environment. Computing module 900 might alsorepresent computing capabilities embedded within or otherwise availableto a given device. For example, a computing module might be found inother electronic devices such as, for example, digital cameras,navigation systems, cellular telephones, portable computing devices,modems, routers, WAPs, terminals and other electronic devices that mightinclude some form of processing capability.

Computing module 900 might include, for example, one or more processors,controllers, control modules, or other processing devices, such as aprocessor 904. Processor 904 might be implemented using ageneral-purpose or special-purpose processing engine such as, forexample, a microprocessor, controller, or other control logic. In theillustrated example, processor 904 is connected to a bus 902, althoughany communication medium can be used to facilitate interaction withother components of computing module 900 or to communicate externally.

Computing module 900 might also include one or more memory modules,simply referred to herein as main memory 908. For example, preferablyrandom access memory (RAM) or other dynamic memory, might be used forstoring information and instructions to be executed by processor 904.Main memory 908 might also be used for storing temporary variables orother intermediate information during execution of instructions to beexecuted by processor 904. Computing module 900 might likewise include aread only memory (“ROM”) or other static storage device coupled to bus902 for storing static information and instructions for processor 904.

The computing module 900 might also include one or more various forms ofinformation storage mechanism 910, which might include, for example, amedia drive 912 and a storage unit interface 920. The media drive 912might include a drive or other mechanism to support fixed or removablestorage media 914. For example, a hard disk drive, a floppy disk drive,a magnetic tape drive, an optical disk drive, a CD or DVD drive (R orRW), or other removable or fixed media drive might be provided.Accordingly, storage media 914 might include, for example, a hard disk,a floppy disk, magnetic tape, cartridge, optical disk, a CD or DVD, orother fixed or removable medium that is read by, written to or accessedby media drive 912. As these examples illustrate, the storage media 914can include a computer usable storage medium having stored thereincomputer software or data.

In alternative embodiments, information storage mechanism 910 mightinclude other similar instrumentalities for allowing computer programsor other instructions or data to be loaded into computing module 900.Such instrumentalities might include, for example, a fixed or removablestorage unit 922 and an interface 920. Examples of such storage units922 and interfaces 920 can include a program cartridge and cartridgeinterface, a removable memory (for example, a flash memory or otherremovable memory module) and memory slot, a PCMCIA slot and card, andother fixed or removable storage units 922 and interfaces 920 that allowsoftware and data to be transferred from the storage unit 922 tocomputing module 900.

Computing module 900 might also include a communications interface 924.Communications interface 924 might be used to allow software and data tobe transferred between computing module 900 and external devices.Examples of communications interface 924 might include a modem orsoftmodem, a network interface (such as an Ethernet, network interfacecard, WiMedia, IEEE 802.XX or other interface), a communications port(such as for example, a USB port, IR port, RS232 port Bluetooth®interface, or other port), or other communications interface. Softwareand data transferred via communications interface 924 might typically becarried on signals, which can be electronic, electromagnetic (whichincludes optical) or other signals capable of being exchanged by a givencommunications interface 924. These signals might be provided tocommunications interface 924 via a channel 928. This channel 928 mightcarry signals and might be implemented using a wired or wirelesscommunication medium. Some examples of a channel might include a phoneline, a cellular link, an RF link, an optical link, a network interface,a local or wide area network, and other wired or wireless communicationschannels.

In this document, the terms “computer program medium” and “computerusable medium” are used to generally refer to media such as, forexample, memory 908, storage unit 920, media 914, and channel 928. Theseand other various forms of computer program media or computer usablemedia may be involved in carrying one or more sequences of one or moreinstructions to a processing device for execution. Such instructionsembodied on the medium, are generally referred to as “computer programcode” or a “computer program product” (which may be grouped in the formof computer programs or other groupings). When executed, suchinstructions might enable the computing module 900 to perform featuresor functions of the disclosed technology as discussed herein.

While various embodiments of the disclosed technology have beendescribed above, it should be understood that they have been presentedby way of example only, and not of limitation. Likewise, the variousdiagrams may depict an example architectural or other configuration forthe disclosed technology, which is done to aid in understanding thefeatures and functionality that can be included in the disclosedtechnology. The disclosed technology is not restricted to theillustrated example architectures or configurations, but the desiredfeatures can be implemented using a variety of alternative architecturesand configurations. Indeed, it will be apparent to one of skill in theart how alternative functional, logical or physical partitioning andconfigurations can be implemented to implement the desired features ofthe technology disclosed herein. Also, a multitude of differentconstituent module names other than those depicted herein can be appliedto the various partitions. Additionally, with regard to flow diagrams,operational descriptions and method claims, the order in which the stepsare presented herein shall not mandate that various embodiments beimplemented to perform the recited functionality in the same orderunless the context dictates otherwise.

Although the disclosed technology is described above in terms of variousexemplary embodiments and implementations, it should be understood thatthe various features, aspects and functionality described in one or moreof the individual embodiments are not limited in their applicability tothe particular embodiment with which they are described, but instead canbe applied, alone or in various combinations, to one or more of theother embodiments of the disclosed technology, whether or not suchembodiments are described and whether or not such features are presentedas being a part of a described embodiment. Thus, the breadth and scopeof the technology disclosed herein should not be limited by any of theabove-described exemplary embodiments.

Terms and phrases used in this document, and variations thereof, unlessotherwise expressly stated, should be construed as open ended as opposedto limiting. As examples of the foregoing: the term “including” shouldbe read as meaning “including, without limitation” or the like; the term“example” is used to provide exemplary instances of the item indiscussion, not an exhaustive or limiting list thereof; the terms “a” or“an” should be read as meaning “at least one,” “one or more” or thelike; and adjectives such as “conventional,” “traditional,” “normal,”“standard,” “known” and terms of similar meaning should not be construedas limiting the item described to a given time period or to an itemavailable as of a given time, but instead should be read to encompassconventional, traditional, normal, or standard technologies that may beavailable or known now or at any time in the future. Likewise, wherethis document refers to technologies that would be apparent or known toone of ordinary skill in the art, such technologies encompass thoseapparent or known to the skilled artisan now or at any time in thefuture.

The presence of broadening words and phrases such as “one or more,” “atleast,” “but not limited to” or other like phrases in some instancesshall not be read to mean that the narrower case is intended or requiredin instances where such broadening phrases may be absent. The use of theterm “module” does not imply that the components or functionalitydescribed or claimed as part of the module are all configured in acommon package. Indeed, any or all of the various components of amodule, whether control logic or other components, can be combined in asingle package or separately maintained and can further be distributedin multiple groupings or packages or across multiple locations.

Additionally, the various embodiments set forth herein are described interms of exemplary block diagrams, flow charts and other illustrations.As will become apparent to one of ordinary skill in the art afterreading this document, the illustrated embodiments and their variousalternatives can be implemented without confinement to the illustratedexamples. For example, block diagrams and their accompanying descriptionshould not be construed as mandating a particular architecture orconfiguration.

What is claimed is: 1-20. (canceled)
 21. A system, comprising: a USBinterface; a coax interface; and a processor configured to: receive apacket, via the USB interface, from a local USB device, transmit aprobe, via the coax interface, over a coaxial network, and receive areply, via the coax interface, from a remote USB device.
 22. The systemof claim 21, wherein: the processor is configured to receive data framesfrom the local USB device via the USB interface, the received dataframes are intended for the remote USB device, and the coaxial networkis operably coupled between the coax interface and the remote USBdevice.
 23. The system of claim 22, wherein: the processor is configuredto: identify, based on header information in the received frames, theremote USB device.
 24. The system of claim 22, wherein: the processor isconfigured to: combine the received data frames into an aggregatedframe, address the aggregated frame to the remote USB device, and sendthe aggregated frame to the remote USB device over the coaxial network.25. The system of claim 24, wherein: the processor is configured to:address the aggregated frame according to addressing protocols of thecoaxial network.
 26. The system of claim 24, wherein: the processor isconfigured to: address the aggregated frame by adding a MoCA frameheader to the aggregated frame.
 27. The system of claim 24, wherein: theprocessor is configured to: address the aggregated frame by adding an IPaddress, associated with the remote USB device, to the aggregated frame.28. The system of claim 24, wherein: the processor is configured to:address the aggregated frame by adding a MAC address, associated withthe remote USB device, to the aggregated frame.
 29. The system of claim21, wherein: the processor is configured to: receive, via the coaxinterface, an aggregated frame from a USB-to-coaxial network bridge, androute individual frames contained in the aggregated frame to apredetermined USB device.
 30. The system of claim 29, wherein: theprocessor is configured to: remove a coaxial network header from theaggregated frame, de-aggregate the individual frames contained in theaggregated frame, read address information associated with theindividual frames, and communicate the individual frames to thepredetermined USB device associated with the address information.
 31. Amethod, comprising: receiving a packet, via a USB interface, from alocal USB device; transmitting a probe, via a coax interface, over acoaxial network; and receiving a reply, via the coax interface, from aremote USB device.
 32. The method of claim 31, wherein the methodcomprises: receiving data frames from the local USB device via the USBinterface, wherein: the received data frames are intended for the remoteUSB device, and the coaxial network is operably coupled between the coaxinterface and the remote USB device.
 33. The method of claim 32, whereinthe method comprises: identifying, based on header information in thereceived frames, the remote USB device.
 34. The method of claim 32,wherein the method comprises: combining the received data frames into anaggregated frame; addressing the aggregated frame to the remote USBdevice; and sending the aggregated frame to the remote USB device overthe coaxial network.
 35. The method of claim 34, wherein the methodcomprises: addressing the aggregated frame according to addressingprotocols of the coaxial network.
 36. The method of claim 34, the methodcomprises: addressing the aggregated frame by adding a MoCA frame headerto the aggregated frame.
 37. The method of claim 34, the methodcomprises: addressing the aggregated frame by adding an IP address,associated with the remote USB device, to the aggregated frame.
 38. Themethod of claim 34, the method comprises: addressing the aggregatedframe by adding a MAC address, associated with the remote USB device, tothe aggregated frame.
 39. The method of claim 31, the method comprises:receiving, via the coax interface, an aggregated frame from aUSB-to-coaxial network bridge; and routing individual frames containedin the aggregated frame to a predetermined USB device.
 40. The method ofclaim 39, the method comprises: removing a coaxial network header fromthe aggregated frame; de-aggregating the individual frames contained inthe aggregated frame; reading address information associated with theindividual frames; and communicating the individual frames to thepredetermined USB device associated with the address information.